home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Tech Arsenal 1
/
Tech Arsenal (Arsenal Computer).ISO
/
tek-20
/
tcp90134.zip
/
TCP90134.TXT
< prev
Wrap
Text File
|
1990-09-14
|
9KB
|
237 lines
Path: tosspot!indep1!pete
From: pete@indep1.UUCP (Peter Franks)
Newsgroups: to.tosspot
Subject: TCP Digest #134
Message-ID: <1335@indep1.UUCP>
Date: 14 Sep 90 01:24:28 GMT
Reply-To: pete@indep1.MCS.COM (Peter Franks)
Followup-To: to.tosspot
Distribution: to
Organization: as little as possible
Lines: 224
TCP-Group Digest Mon, 10 Sep 90 Volume 90 : Issue 134
Today's Topics:
Choosing an SSID (4 msgs)
Mailbox ID
RSPF problems
rspf status.
RSPF version doesn't do ARP replies
Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>
Send requests of an administrative nature (addition to, deletion from the
distribution list, et al) to: <ListServ@UCSD.Edu>
Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".
----------------------------------------------------------------------
Date: Sun, 9 Sep 90 08:47:22 -0700
From: brian (Brian Kantor)
Subject: Choosing an SSID
To: packet-radio, tcp-group
Originally the AX.25 SSID (secondary station identifier) was more or
less intended for those who had multiple stations to be able to
differentiate between them even though they had the same callsign.
Thus WB6CYT-1 and WB6CYT-0.
However, they're immensely useful in selecting the FUNCTION that a
particular connection provides. For example, -0 is a person, -1 is a
digipeater, -2 is a BBS, -3 is TCP/IP, etc. Whether these are just
logical separations or whether it is actually utilising different
equipment is usually moot from the standpoint of the person connecting.
Of course, with net/rom complementing the SSID every time it
masquerades as a connecting user, such distinctions may well make no
difference. But in more enlightened areas where net/rom does not hold
sway, the differing SSIDs could be useful.
The examples above are somewhat common in my area, but not universal.
Is there any sort of consensus as to which SSID should be used for what?
- Brian
------------------------------
Date: Sun, 9 Sep 90 14:40:29 CDT
From: brainiac!jrc (Jeffrey Comstock)
Subject: Choosing an SSID
To: shamash!ucsd.edu!tcp-group@umn-cs.cs.umn.edu
Here is what is going on in the Minnesota area:
-0 Mixture of RLI bbs's, Keyboard to Keyboard, Personnal
mailboxes on Kantronics and AEA TNC's.
-1 Keyboard to Keyboard.
-3 Msys BBS's.
-9 Netrom and TCP/IP.
-15 The first hop from a netrom.
The -9 for TCP/IP and Netrom is because initially most connects
to the TCP/IP stations were via Netrom connections.
It seems that -7 is the international designation for KA-Nodes.
Jeff
------------------------------
Date: Sun, 9 Sep 90 23:31:43 EDT
From: crompton@NADC.NADC.NAVY.MIL (D. Crompton)
Subject: Choosing an SSID
To: brian@ucsd.edu, packet-radio@ucsd.edu, tcp-group@ucsd.edu
For whatever reason we in the Mid Atlantic area are (generally) using
-8 as TCP/IP SSID with IPxxx as netrom ID - I.E. wa3dsp - IPDSP
Doug
------------------------------
Date: Mon, 10 Sep 90 10:10:18 BST
From: Dave Lockwood <vision!davel@relay.EU.net>
Subject: Choosing an SSID
To: tcp-group@ucsd.edu
Here in the UK, the use of SSIDs is sorta "standardised". But like most
standards, we have quite a few of 'em :-).
Our Net/Rom Nodes and BBSs require special licenses from our DTI (=FCC).
Net/Roms are GB7+two letters and BBSs are GB7+3.
In this group, the "standard" is:
-0 No recommendation
-1 Microwave
-2 144 MHz
-3 HF
-4 70MHz (4 metre band)
-5 TCP/IP
-6 50MHz
-7 432MHz
The rest are also "no recommendation". As here such stations proliferate to
a ridiculous degree (my home town of Wakefield pop 75000) has three BBSs
serving it, all providing exactly the same functionality), users get used
to seeing the SSIDs used as above and tend to adopt the same principle.
There's certainly no legal reinforcement of the above, indeed it's interesting
to note that the licensing authority views the callsigns embedded in the
address field of AX.25 frames as irrelevant and are not judged to be
"identification". Callsigns in plain text (in the info field) are.
Returning to SSIDs, when I allocate an Amprnet address, the text I send
to the requestor includes a sentence: "When operating your TCP/IP station
the recommended callsign/SSID is 'G9XYZ-5'". The majority of users
comply, but I've noticed the ones who don't tend to be TCP/IP gurus.
Is there a lesson here (lotsa :-) before the flames start).
73
--
-------------------- I'm totally incommunicado, except for ---------------------
Dave Lockwood ...!uunet!mcsun!ukc!vision!davel davel@vision.uucp
Technical Consultant ...!uunet!bulus3!bungia!vware!davel davel@vware.MN.ORG
VisionWare Ltd, G4CLI@GB7YHF.194.GBR.EU dave@g4cli.ampr.org
57 Cardigan Lane, D.LOCKWOOD@ICLX davel@vision.co.uk
Leeds, LS4 2LE, +44-532-788858 +44-831-494088
United Kingdom +44-532-304676 "Hey, You!"
----------------------- VISIONWARE DOS/UNIX INTEGRATION ------------------------
------------------------------
Date: Sun, 9 Sep 90 23:34:32 EDT
From: crompton@NADC.NADC.NAVY.MIL (D. Crompton)
Subject: Mailbox ID
To: tcp-group@ucsd.edu
A local BBS operator has requested that the NOS BBS ID be changed
from [NET-$] to [NET-H$] - this was done in net towards the end but
somehow got lost in NOS.
Doug
------------------------------
Date: Sun, 9 Sep 90 23:46:19 EDT
From: crompton@NADC.NADC.NAVY.MIL (D. Crompton)
Subject: RSPF problems
To: tcp-group@ucsd.edu
We implemented RSPF on our 2 meter TCP/IP network and had very bad
results. IT was implemented as per Anders note. I have to admit that
I have been very busy and have not had a chance to thoroughly read the
RSPF paper. Here is what we are seeing -
Jheard (ax heard) list is nothing but garbage.
Hard coded routes (for all interfaces) are lost after
a few hours of operation. This is with 'rspf attach' on just
one interface. After this happens ONLY rspf equiped stations
update the route list. All other routes (net stations and non
rspf NOS) are lost.
Minor note - the reporting router message at trace reverses the
displayed IP address - I.E 44.80.0.70 displays 70.0.80.44
We have suspended operation of RSPF to see if there is some other
code problem in the latest G1EMM version.
Maybe someone could explain what we should see? Should we see routes
added in the route list? Can hard coded routes still exist and not
be bothered? Should they be route add privates maybe? Should you
normally not add any routes on the rspf interface and just let it do
it's work?
I think there should be more status info from RSPF. At the moment you
have to trace to see anything. Something like 'rspf status'.
Doug
------------------------------
Date: Mon, 10 Sep 90 11:24:20 GMT
From: kelvin@kelvin.uk22.bull.com
Subject: rspf status.
To: tcp-group@ucsd.edu
Doug et al,
rspf status is implemented in 900828 v1.1 and I have fixed the reversed
host address on the trace. I have noted all the problems you guys have seen
with routes being lost etc. I haven't seen any ax25 heard list corruption
however. I'll look into that just in case ax25.h has somehow got changed to
the version with the TX fifo in use. I don't really want to try and debug
too much of rspf as it is really Fred and Anders baby and they are best
equipped to analyse coding and protocol faults. I'll look at the ARP bug
though.. Thats a bit too serious to leave. I think 90082811.exe/zip are
up on thumper. If not, I'll put the latest I have up A.S.A.P.
All the best,
Kelvin.
+-------------------------------------------------+
| Kelvin J.Hill - BULL HN Ltd, Hounslow, England. |
| Internet - kelvin.uk22.bull.com [128.35.110.6] |
| Amprnet - g1emm.ampr.org [44.131.7.6] |
+-------------------------------------------------+
------------------------------
Date: Sun, 9 Sep 90 10:59:57 CDT
From: Jay Maynard <jmaynard@thesis1.hsch.utexas.edu>
Subject: RSPF version doesn't do ARP replies
To: tcp-group@ucsd.edu
I built a version of NOS 900828 with Anders Klemets' RSPF and FORTH code
included last night. It seemed to work OK, except that it wouldn't reply to
an ARP request for its own address. I tried an arp publish, and that didn't
help matters any. Stock 900828 works fine. Any ideas? I hadn't started any
RSPF timers yet, but starting them made no difference. Thanks...
------------------------------
End of TCP-Group Digest
******************************
--
+------------------------------------------------------------------------------+
| Peter Franks | pete@indep1.mcs.com OR pete@indep1.uucp |
| NI9D | Use whichever one works |
+------------------------------------------------------------------------------+